This was about as straightforward as I expected though it turns out the conventional commit header pattern does not allow - characters meaning that also needs to be changed for Jira keys - it would be great if that was handled by the action either by just changing the default pattern entirely or by changing it when a custom type (or maybe even a "probably a regexp" type?) is detected, but either way that's out of scope for this particular change (let me know if you'd be open to it though).

The primary use case for this action is to match PR titles against the Conventional Commits spec. I think I'd prefer to stick to their defaults to avoid surprises.

Also something else this would be useful with is the ability to add additional types, rather than having the default list overridden - I'm happy to create a follow up issue and PR if that sounds useful.

I think API-wise this might be a bit tough to get in. We already have a config option to use entirely different types, so this would likely mean another config option, which can essentially be used for the same thing. Sorry, I think also here I'd prefer to keep the action a bit more minimalistic!

Sorry for pushing back a bit here, I hope this makes sense!

🎉 This PR is included in version 6.1.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀